Skip to content

fix: test storybook action#35585

Merged
KelvinOm merged 4 commits intoreleasefrom
fix/storybook-test-action
Aug 9, 2024
Merged

fix: test storybook action#35585
KelvinOm merged 4 commits intoreleasefrom
fix/storybook-test-action

Conversation

@KelvinOm
Copy link
Collaborator

@KelvinOm KelvinOm commented Aug 9, 2024

Description

Example of a successful pass:
https://github.com/appsmithorg/appsmith/actions/runs/10321826794/job/28575617540

Automation

/ok-to-test tags=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

  • Yes
  • No

Summary by CodeRabbit

  • Chores
    • Streamlined GitHub Actions workflow for testing Storybook by consolidating Playwright installation and removing redundant steps.
    • Enhanced clarity and efficiency of the testing process.
  • Style
    • Updated button component styles by disabling rounded corners, reflecting a potential shift in design strategy.

@KelvinOm KelvinOm requested a review from sharat87 as a code owner August 9, 2024 14:32
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 9, 2024

Walkthrough

The recent updates to the GitHub Actions workflow enhance the efficiency of testing Storybook by streamlining the Playwright installation and eliminating redundant steps. This results in a clearer process where tests run directly within the Storybook context, improving overall performance and reducing complexity.

Changes

File Change Summary
.github/workflows/test-storybook.yml Consolidated Playwright installation into the dependency step and removed the separate serving process for tests.
app/client/packages/design-system/widgets/src/components/Button/src/styles.module.css Removed the border-radius property, indicating a design shift while maintaining other styling elements.

Sequence Diagram(s)

sequenceDiagram
    participant A as Developer
    participant B as GitHub Actions
    participant C as Storybook
    participant D as Playwright

    A->>B: Push changes
    B->>D: Install Playwright
    B->>C: Run Storybook tests
    C-->>B: Return test results
    B-->>A: Notify test completion
Loading

Poem

In the realm of code where we strive for grace,
A simpler journey we've now embraced.
Playwright awaits, no steps left behind,
Swiftly we test, with clarity aligned.
Styles shift gently, as design takes flight,
Cheers to the changes, making our path bright! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the Bug Something isn't working label Aug 9, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 42debc6 and 8f6582e.

Files selected for processing (1)
  • .github/workflows/test-storybook.yml (1 hunks)
Additional comments not posted (1)
.github/workflows/test-storybook.yml (1)

43-44: Good job on reordering the Playwright installation step!

By installing Playwright before running the Storybook tests, you ensure that all necessary dependencies are set up beforehand. This is a great practice to prevent potential test failures due to missing dependencies.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (1)
app/client/packages/design-system/widgets/src/components/Button/src/styles.module.css (1)

13-13: Consider the impact of removing border-radius.

Commenting out the border-radius property will result in buttons having sharp corners, which might not align with the overall design aesthetic. Ensure this change is consistent with the design guidelines and does not negatively affect the user experience. If this is intentional, consider documenting the design decision.

Tools
Biome

[error] 13-13: Expected a declaration, or an at rule but instead found '//'.

Expected a declaration, or an at rule here.

(parse)

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8f6582e and 565e9e2.

Files selected for processing (1)
  • app/client/packages/design-system/widgets/src/components/Button/src/styles.module.css (1 hunks)
Additional context used
Biome
app/client/packages/design-system/widgets/src/components/Button/src/styles.module.css

[error] 13-13: Expected a declaration, or an at rule but instead found '//'.

Expected a declaration, or an at rule here.

(parse)

@KelvinOm KelvinOm force-pushed the fix/storybook-test-action branch 3 times, most recently from 36b1847 to c98df1f Compare August 9, 2024 15:06
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 565e9e2 and c98df1f3933553c75659e5e4fd0a2c3f78fa1c1a.

Files selected for processing (1)
  • .github/workflows/test-storybook.yml (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/test-storybook.yml

@KelvinOm KelvinOm force-pushed the fix/storybook-test-action branch from c98df1f to 7dd9474 Compare August 9, 2024 15:32
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c98df1f3933553c75659e5e4fd0a2c3f78fa1c1a and 7dd9474.

Files selected for processing (2)
  • .github/workflows/test-storybook.yml (1 hunks)
  • app/client/packages/design-system/widgets/src/components/Button/src/styles.module.css (1 hunks)
Files skipped from review due to trivial changes (1)
  • app/client/packages/design-system/widgets/src/components/Button/src/styles.module.css
Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/test-storybook.yml

@KelvinOm KelvinOm requested a review from albinAppsmith August 9, 2024 15:45
@KelvinOm KelvinOm merged commit 8bf6df5 into release Aug 9, 2024
@KelvinOm KelvinOm deleted the fix/storybook-test-action branch August 9, 2024 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants